fix(lambda-tiler): ensure wmts limits extent to the bounding box of the tile matrix extent BM-1012 #3235
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
As we recently changed the basemaps configuration to use the raw tiff values for extent rather than the name of the tile, the extents of each layer has slightly changed.
This works for most layers except ones which cover the entire world, for example
0-0-0.tiff
this can lead to slight floating point errors in the extents between the TileMatrix and the tiff.Modification
If the imagery extent is outside the bounds of the tile matrix fall back to the extent of the tile matrix.
Checklist
If not applicable, provide explanation of why.